Columbia Kermit/kermit.zip/newsgroups/misc.19950929-19951130/[e-mail]_Wed Nov 1 23:15:15 1995.msg

Internet Message Format | 2020-01-01 | 4KB

Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA24469
  (5.65c+CU/IDA-1.4.4/HLK for <[e-mail]>); Fri, 3 Nov 1995 10:05:09 -0500
Received: by apakabar.cc.columbia.edu id AA18551
  (5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Fri, 3 Nov 1995 10:05:08 -0500
Path: news.columbia.edu!sol.ctr.columbia.edu!news.kei.com!news.mathworks.com!uunet!in2.uu.net!csn!nntp-xfer-2.csn.net!silo.nrcs.usda.gov!ftcnews.nrcs.usda.gov!feinde2.ftc.nrcs.usda.gov!ute
From: [e-mail] (Ute R. Willmore)
Newsgroups: comp.protocols.kermit.misc
Subject: MS-kermit and APC codes (LONG)
Date: 1 Nov 1995 23:15:15 GMT
Organization: USDA-SCS NHQ in Fort Collins
Lines: 74
Message-Id: <478v23$[e-mail]>
Nntp-Posting-Host: feinde2.ftc.nrcs.usda.gov
X-Newsreader: TIN [version 1.2 PL2]
Apparently-To: [e-mail]

I am still having some problems getting MS-Kermit to do what I want it
to do. Last time I posted, I couldn't turn of the file display on the DOS side
from the UNIX side. I got that figured out now. Sorry, Frank, but your answer
to my question was incorrect, but I appreciate the help anyway. I decided to
give a very detailed account of what I am doing this time, to avoid misunder-
standings.

Anyway, now I am trying to determine if a file exists on the my DOS system,
and if so send that file to the UNIX system, otherwise, I want to give some
indication of the error to UNIX, to prevent C-Kermit from getting started.
Remember I am doing all of this kind of backwards. I start MS-Kermit on
my DOS system which is hooked to my UNIX system via a serial connection. Then
I run some program on my UNIX system that needs to tranfer files back and
forth to the DOS system. So I have to do system calls that look something like
this:

echo "\033_send c:\mydir\myfile\033\\"; kermit -r -a /tmp/myfile

This works just fine IF c:\mydir\myfile exists, otherwise, C-Kermit starts
and puts up a "ready to receive " message and then waits for the user to issue
a send command on the DOS side. Of course, that user input would never happen.

As a work around, I create script file that I send to DOS, and then tell
MS-Kermit to take that script. ie.

echo "\033_receive my_script\033\\" ; kermit -s my_script
echo "\033_take my_script\033\\" ; kermit -r receive

where my_script looks something like this:

if exists c:\mydir\my_file send c:\my_dir\my_file
if not exists c:\my_dir\my_file send my_script

This works okay. Since I send something for sure, C-Kermit doesn't hang, and
once I have the file on my UNIX system I can figure out if it is data or my
script. It's ugly and but there are some problems.

1) I can't delete my_script, i.e. putting 'run del my_script' inside the
   script has no effect. How come?

2) I would prefer to just send some error return (rather than my_script)
   if the data file doesn't exist. I tried using 'output ERROR' in the second
   if but it doesn't arrive on my UNIX system. Am I missing something?

3) If this ugly way is the only way, I need to reset file collision before I
   send my_script to the DOS system. That's easy enough to do with

   echo "\033_set file collision overwrite\033\\"

   and my_script would include the command to set file collision to what ever
   it was before. But, here is the problem: How can I determine what file
   callision was set to, save that information, and then use it to reset
   file collision when my_script is done?

4) Is there a GOOD source on using APC codes and MS-Kermit? I have read most
   of Using MS-Kermit and Using C-Kermit, but neither one mentions them. The
   .bwr files mention them but not in detail.

Okay that should do it for today. BTW, I am running MS-Kermit 3.13 Patch
level 0 dated July 8 1993 under DOS 6.2 and C-Kermit 5A(190) for UnixWare
dated Oct/4/94 under UnixWare (thats Unix 4.2 I think).


Thanks for reading this and thanks for any help.

Ute

---------------------------------------------------------------------------

Life is a game that must be played.
The rules of the games are known to us as the Laws of Nature.


e-mail:  [e-mail]